Systems and methods for wireless transmission of power

ABSTRACT

Systems and methods for real time communication between wireless power transmitters and wireless power receivers based on software embedded on a microprocessor. The systems and methods described here may allow wireless power transmitters to communicate with one or more wireless power receivers in real time within intervals of one second. The systems and methods described here may also enable full control of the wireless power receivers by letting the user decide which wireless power receivers to charge, when to charge them, and set priorities and charging schedules among other functions.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present disclosure is related to U.S. non-provisional patent application DWV-3DPF-010 entitled “Methodology for Pocket-forming”; and DWV-3DPF-028 entitled “Methodology for Multiple Pocket-Forming”; DWV-3DPF-015 entitled “Method for 3 Dimensional Pocket-forming”; DWV-3DPF-027 entitled “Receivers for Wireless Power Transmission”; DWV-3DPF-029 entitled “Transmitters for Wireless Power Transmission,” all of which are invented by Michael Leabman, and all of which are incorporated herein by reference in their respective entireties.

BACKGROUND

1. Field of the Disclosure

The present disclosure relates generally to software embedded on a chip, and more specifically to software embedded on a chip that controls the communication between a wireless power transmitter and one or more wireless power receivers in real time.

2. Background Information

Electronic devices such as laptop computers, smartphones, portable gaming devices, tablets and so forth require power for performing their intended functions. This may require having to charge electronic equipment at least once a day, or in high-demand electronic devices more than once a day. Such an activity may be tedious and may represent a burden to users. For example, a user may be required to carry chargers in case his electronic equipment is lacking power. In addition, users have to find available power sources to connect to. Furthermore, users must plug into a wall or other power supply to be able to charge their electronic device. However, such an activity may render electronic devices inoperable during charging. Some approaches to this problem may include inductive pads which may employ magnetic induction or resonating coils. Nevertheless, such a solution may still require that electronic devices may have to be placed in a specific place for powering. Thus, electronic devices during charging may not be portable.

Other approach may include using RF waves through suitable power transmission techniques such as pocket-forming. This approach may provide wireless power transmission while eliminating the use of wires or pads for charging devices which may require tedious procedures such as plugging to a wall, and may turn devices unusable during charging. In addition, electronic equipment may require less components as typical wall chargers may not be required. In some cases, even batteries may be eliminated as a device may fully be powered wirelessly.

Although the latter approach may significantly solve the problem of using wires or pads for charging devices, the communication controls among wireless power devices using this approach may demand a real time communication (high transfer rate) and may not be easily achieved. There are a few off-the-shelf solutions that allow the fast communication between these devices, however these solutions may encounter a limited number of packets sent per second, hence a real time communication may not be reached. For the foregoing reasons, there is a need for a system and method that allows real time communication among wireless power devices so as to have a better control of them.

SUMMARY

Embodiments in the present disclosure may be directed to provide systems and methods for real time communication between wireless power transmitters and wireless power receivers based on software embedded on a microprocessor.

In one aspect of the present disclosure, a system architecture that may enable the communication controls between wireless power transmitter and one or more wireless power receivers is disclosed. Wireless powered receivers may include covers and customer pocket-forming enabled devices.

In one aspect, a wireless power transmitter may include a microprocessor that integrates a power transmitter manager app (PWR TX MGR APP) which may include a database for storing relevant information from wireless power receivers, and a third party application programming interface (Third Party API) for a Bluetooth Low Energy chip (BTLE CHIP HW). The wireless power transmitter may also include antenna manager software (Antenna MGR Software) to control an RF antenna array that may be used to form controlled RF waves which may converge in 3-D space and create pockets of energy on wireless power receivers (covers and customer pocket-forming enabled devices).

In another aspect, a cover may include a power receiver app (PWR RX APP), a third party application programming interface (Third party API) for a Bluetooth Low Energy chip (BTLE CHIP HW), and a radio frequency (RF) antenna array which may be used to receive and utilize the pockets of energy sent from wireless power transmitter.

As used herein, a customer pocket-forming enabled device may refer to a wireless device such as a smartphone, tablet, or the like that may include an integrated wireless power receiver chip (not shown in FIG. 1) for wireless power charging. Customer pocket-forming enabled devices may include a power receiver app (PWR RX APP), and a third party application programming interface (Third Party API) for a Bluetooth Low Energy chip (BTLE CHIP HW). Customer pocket-forming enabled devices may also include an RF antenna array which may be used to receive and utilize pockets of energy sent from wireless power transmitter. GUI may be downloaded from any suitable application store and may run on any suitable operating system such as iOS and Android, among others.

In another aspect of the present disclosure, a sequence diagram that illustrates the interactions between the GUI, third party API and power manager app in the power transmitter board, and power receiver app and power receiver API in the power receiver board, is disclosed.

In one embodiment, power transmitter manager app may scan for ads emitted from power receivers and GUI. Power receiver ads may send data to power transmitters that may include a unique ID, and at the same time GUI may also send data to power transmitters that may include a list of power receivers to track and to be charged. Once power transmitter manager app reads and processes the data received from both, the power receiver and the GUI, it may attempt connection with the power receiver. Once the connection is established, a connection callback is sent to the power transmitter manager app in order to start communication with the power receiver to which is connected. Thereafter, the power transmitter manager app may send a start communication write request message to the power receiver app. Power receiver API may immediately send a call back to the power receiver app in order to start sending messages back to the power transmitter manager app. In an embodiment, the messages may be sent up to a rate of about 100 packets per second, however in other embodiments the transfer rate may go even up to 400 packets per second or more. These messages may include status and data from the power receiver board such as battery levels, charging status, and antenna voltage among others.

When the power transmitter manager app receives said messages, an immediate call back from the third party API of the power transmitter board is sent to the power transmitter manager app stating that the message has been received. There may be a callback for each message received. However, the power receiver API, after a certain period of time, may run out of transmit buffers, and hence the power receiver app may call a function in the API to get the status of transmit buffers. Then the power receiver app may indicate this in the status of the next message to the power transmitter manager app. Subsequently, the power transmitter manager app may immediately send a start communication write request message back to the power receiver app to restore the transmit buffers. As a result, transmit buffers may be restored and the power receiver API may call again the power receiver app to send status and data messages to the power transmitter manager app until it runs out of buffers. However, the power transmitter manager app, at this point may stop sending a start communication write request message again to restore the transmit buffers. Instead, the power transmitter manager app may do another scan to listen for ads from other wireless power receivers and the GUI. GUI may then tell the power transmitter manager app which wireless power receivers to track and to be charged. Finally the negotiation process to establish a real time communication with the next wireless power receiver may repeat again. Thereafter periodically, such as every one second, the power transmitter manager app may search for other wireless power receivers so as to keep its information of all wireless power receivers around its radio updated.

The above described systems and methods may allow wireless power transmitters to communicate with one or more wireless power receivers in real time within intervals of one second. The systems and methods described here may enable full control of the wireless power receivers by letting the user decide which wireless power receivers to charge, when to charge them, and set priorities and charging schedules among other functions. In other embodiments, the systems and methods described here may allow the wireless power transmitters to communicate with wireless power receivers simultaneously by adding multiple BTLE chips on the power transmitter board.

Numerous other aspects, features and benefits of the present disclosure may be made apparent from the following detailed description taken together with the drawing figures.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure can be better understood by referring to the following figures. The components in the figures are not necessarily to scale, emphasis instead being placed upon illustrating the principles of the disclosure. In the figures, reference numerals designate corresponding parts throughout the different views.

FIG. 1 shows a system architecture in which one or more embodiments of the present disclosure may operate.

FIG. 2 shows a sequence diagram of real time communication between wireless power transmitters and wireless power receivers, according to an embodiment.

DETAILED DESCRIPTION

The present disclosure is here described in detail with reference to embodiments illustrated in the drawings, which form a part here. Other embodiments may be used and/or other changes may be made without departing from the spirit or scope of the present disclosure. The illustrative embodiments described in the detailed description are not meant to be limiting of the subject matter presented here.

DEFINITIONS

As used here, the following terms may have the following definitions:

“Real time communication” refers to communicating the status of data at the receiver at the continuing present time, where a proprietary algorithm may read the present state of important information at the receiver continually and rapidly with only 1/100 of a second of delay.

“Transmitter” may refer to a device, including a chip which may generate two or more RF signals, at least one RF signal being phase shifted and gain adjusted with respect to other RF signals, substantially all of which pass through one or more RF antennas such that focused RF signals are directed to a target.

“Receiver” may refer to a device including at least one antenna element, at least one rectifying circuit and at least one power converter, which may utilize pockets of energy for powering or charging an electronic device.

“Pocket-forming” may refer to generating two or more RF waves which converge in 3-D space, forming controlled constructive and destructive interference patterns.

“Pockets of energy” may refer to areas or regions of space where energy or power may accumulate in the form of constructive interference patterns of RF waves.

“Ad” may refer to one or more Bluetooth Low Energy (BTLE) advertisement messages transmitted from a BTLE device.

Reference will now be made to the exemplary embodiments illustrated in the drawings, and specific language will be used here to describe the same. It will nevertheless be understood that no limitation of the scope of the invention is thereby intended. Alterations and further modifications of the inventive features illustrated here, and additional applications of the principles of the inventions as illustrated here, which would occur to one skilled in the relevant art and having possession of this disclosure, are to be considered within the scope of the invention.

FIG. 1 shows a system architecture 100 in which one or more embodiments of the present disclosure may operate. System architecture 100 may enable the communication controls between wireless power transmitter 102 and one or more wireless power receivers. Wireless power receivers may include covers 104 and customer pocket-forming enabled devices 106.

In one embodiment, wireless power transmitter 102 may include a microprocessor that integrates a power transmitter manager app 108 (PWR TX MGR APP), and a third party application programming interface 110 (Third Party API) for a Bluetooth Low Energy chip 112 (BTLE CHIP HW). Wireless power transmitter 102 may also include an antenna manager software 114 (Antenna MGR Software) to control an RF antenna array 116 that may be used to form controlled RF waves which may converge in 3-D space and create pockets of energy on wireless power receivers (covers 104 and customer pocket-forming enabled devices 106). In an embodiment, Bluetooth Low Energy chip 112 may be replaced by another type of wireless protocol such as WiFi or the like.

Power transmitter manager app 108 may store relevant information from wireless power receivers such as, identifiers, voltage ranges, location, signal strength and/or any relevant information from a wireless power receivers. For example, the power transmitter app 108 may store the relevant information in a database (not shown).

Power transmitter manager app 108 may call third party application programming interface 110 for running a plurality of functions such as start a connection, end a connection, and send data among others. Third party application programming interface 110 may command Bluetooth Low Energy chip 112 according to the functions called by power transmitter manager app 108.

Third party application programming interface 110 at the same time may call power transmitter manager app 108 through a callback function which may be registered in the power transmitter manager app 108 at boot time. Third party application programming interface 110 may have a timer callback that may go for ten times a second. Third party application programming interface 110 may send callbacks every time a connection begins, a connection ends, a connection is attempted, or a message is received.

Covers 104 may include a power receiver app 118 (PWR RX APP), a third party application programming interface 120 (Third party API) for a Bluetooth Low Energy chip 122 (BTLE CHIP HW), and a RF antenna array 124 which may be used to receive and utilize the pockets of energy sent from wireless power transmitter 102.

Power receiver app 118 may call third party application programming interface 120 for running a plurality of functions such as start a connection, end the connection, and send data among others. Third party application programming interface 120 may have a timer callback that may go for ten times a second and may send callbacks every time a connection begins, a connection ends, a connection is attempted, or message is received.

Covers 104 may be paired to a wireless device such as a smartphone, or tablet via a BTLE connection 126 by using a graphical user interface (GUI 128) that may be downloaded from any suitable application store and may run on any suitable operating system such as iOS and Android, among others. Covers 104 may also communicate with wireless power transmitter 102 via a BTLE connection 126 to send important data such as an identifier for the device as well as battery level information, antenna voltage, geographic location data, or other information that may be of use for the wireless power transmitter 102.

In other embodiments, GUI 128 may also be installed on a wireless device (smartphones or tablets) that may not have the cover 104. GUI 128 may perform operations to communicate with power transmitter manager app 108 via BTLE connection 126 or any other wireless communication protocols such as WiFi among others.

Customer pocket-forming enabled devices 106 may refer to a wireless device such as smartphones, tablets, or any of the like that may include an integrated wireless power receiver chip (not shown in FIG. 1) for wireless power charging. Customer pocket-forming enabled devices 106 may include a power receiver app 130 (PWR RX APP), and a third party application programming interface 132 (Third Party API) for a Bluetooth Low Energy chip 134 (BTLE CHIP HW). Customer pocket-forming enabled devices 106 may also include an RF antenna array 136 which may be used to receive and utilize pockets of energy sent from wireless power transmitter 102. GUI 138 may be downloaded from any suitable application store and may run on any suitable operating system such as iOS and Android, among others.

Power receiver app 130 may call third party application programming interface 132 for running a plurality of functions such as start a connection, end the connection, and send data among others. Third party application programming interface 132 may have a timer callback that may go for ten times a second and may send callbacks every time a connection begins, a connection ends, a connection is attempted, or message is received.

Customer pocket-forming enabled devices 106 may also communicate with wireless power transmitter 102 via a BTLE connection 126 to send important data such as an identifier for the device as well as battery level information, antenna voltage, geographic location data, or other information that may be of use for the wireless power transmitter 102.

FIG. 2 shows a sequence diagram 200 for a real time communication between wireless power transmitters and wireless power receivers, according to an embodiment.

Sequence diagram 200 illustrates the interactions between objects or roles that allow the real time communication between a wireless power transmitter and one or more wireless power receivers. The objects or roles described here may include, but is not limited to, a GUI 202, a third party API 204 that controls a BTLE chip embedded on the power transmitter board, a power transmitter manager app 206, a power receiver app 208, and a power receiver API 210 that controls a BTLE chip embedded on a wireless power receiver board.

Power transmitter manager app 206 may first scan for power receivers ads every one second as long as its radio receiver is on. Power receiver app 208 may continuously broadcast ads 212 around its radio until a power transmitter manager app 206 intercepts these ads 212. Ads 212 may include data such as unique IDs that may allow power transmitter manager app 206 to identify the wireless power receiver to which is about to establish a connection. Once power transmitter manager app 206 intercepts ads 212, it may attempt connection one or more times until it gets connected. GUI 202, at the same time, may continuously send ads 214 to third party API 204 on the transmitter board until it causes an add detection callback that may initiate timer callback 216 in the third party API 204. Ads 214 may include data such as a list of power receivers to be tracked and which to be charged.

Timer callback 216 may then trigger power transmitter manager app 206 where power transmitter manager app 206 may respond by sending a start communication 218 write request message to power receiver app 208 to initiate real time communication with power receiver app 208. Then power receiver API 210 may respond with a callback 220 sent to power receiver app 208 which may immediately trigger power receiver app 208 by sending multiple messages including status and data 222 of the wireless power receiver, at a rate of about 100 packets per second, to the power transmitter manager app 206. Status and data 222 may include data such as antenna voltage of the wireless power receiver, battery levels, and charging status among others. In other embodiments, the transfer rate may go up to 400 packets per second but there may be problems of communication at that rate.

After status and data 222 is received at power transmitter manager app 206, third party API 204 sends a message received call back 224 to power transmitter manager app 206. Then power transmitter manager app 206 processes the status and data 222 message. This process may repeat every time a status and data 222 is received. After a certain period of time, power receiver app 208 may send a status indicating that power receiver API 210 is running out of transmit buffers. Subsequently, power transmitter manager app 206 may restore the buffers by sending back a start communication 226 write request message to the power receiver app 208. Once the buffers are restored, a callback 228 from the power receiver API 210 is sent to the power receiver app 208, triggering the software to send status and data 230 again back to power transmitter manager app 206 at a rate of about 100 packets per second. Status and data 230 may continue to send updates about antenna voltage of the wireless power receiver, battery levels, and charging status among others.

After status and data 230 is received at power transmitter manager app 206, third party API 204 sends a message received call back 232 to power transmitter manager app 206. Then power transmitter manager app 206 processes the status and data 230 message. This process may repeat every time a status and data 222 is received. After a certain period of time, power receiver app 208 may send a status indicating that power receiver API 210 is running out of transmit buffers. However, at this point, power transmitter manager app 206 may check the time and realize that one second has gone since it started communication with power receiver app 208, hence it may be time to check if there are other wireless power receivers that may need charge. Power transmitter manager app 206 may then stop restoring buffers on power receiver API 210 and set on a scanning mode where it listens for ads coming from GUI 202 and power receiver APP 208. Subsequently, GUI 202 may send ads 234 to third party API 204 which my trigger a timer callback 236. Ads 234 may include data such as a list of power receivers to be tracked and which to be charged. Power transmitter manager app 206 may then process ads 234 and establish a real time communication with the next wireless power receiver available within a period of one second.

The above described systems and methods may allow wireless power transmitters to communicate with one or more wireless power receivers in real time within intervals of one second. The systems and methods described here may enable full control of the wireless power receivers by letting the user decide which wireless power receivers to charge, when to charge them, and set priorities and charging schedules among other functions. In other embodiments, the systems and methods described here may allow the wireless power transmitters to communicate with wireless power receivers simultaneously by adding multiple BTLE chips on the power transmitter board.

The foregoing method descriptions and the process flow diagrams are provided merely as illustrative examples and are not intended to require or imply that the steps of the various embodiments must be performed in the order presented. As will be appreciated by one of skill in the art the steps in the foregoing embodiments may be performed in any order. Words such as “then,” “next,” etc. are not intended to limit the order of the steps; these words are simply used to guide the reader through the description of the methods. Although process flow diagrams may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination may correspond to a return of the function to the calling function or the main function.

The various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed here may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

Embodiments implemented in computer software may be implemented in software, firmware, middleware, microcode, hardware description languages, or any combination thereof. A code segment or machine-executable instructions may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, etc.

The actual software code or specialized control hardware used to implement these systems and methods is not limiting of the invention. Thus, the operation and behavior of the systems and methods were described without reference to the specific software code being understood that software and control hardware can be designed to implement the systems and methods based on the description here.

When implemented in software, the functions may be stored as one or more instructions or code on a non-transitory computer-readable or processor-readable storage medium. The steps of a method or algorithm disclosed here may be embodied in a processor-executable software module which may reside on a computer-readable or processor-readable storage medium. A non-transitory computer-readable or processor-readable media includes both computer storage media and tangible storage media that facilitate transfer of a computer program from one place to another. A non-transitory processor-readable storage media may be any available media that may be accessed by a computer. By way of example, and not limitation, such non-transitory processor-readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other tangible storage medium that may be used to store desired program code in the form of instructions or data structures and that may be accessed by a computer or processor. Disk and disc, as used here, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media. Additionally, the operations of a method or algorithm may reside as one or any combination or set of codes and/or instructions on a non-transitory processor-readable medium and/or computer-readable medium, which may be incorporated into a computer program product.

The preceding description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined here may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown here but is to be accorded the widest scope consistent with the following claims and the principles and novel features disclosed here. 

1. A system for controlling communication between a wireless power transmitter and at least one wireless power receiver, the system comprising: a wireless power transmitter that includes: a microprocessor running a power transmitter manager application; wireless communication hardware having an application programming interface (API) operatively coupled with the power transmitter manager application; a transmitter radio frequency (RF) antenna array controlled by transmitter antenna manager software running on the transmitter microprocessor, arranged to form controlled RF waves that converge to create pockets of energy in the space proximate the wireless power transmitter at least partially responsive to the power manager application; and at least one wireless power receiver that includes: a microprocessor running a power receiver application; wireless communication hardware having a receiver API operatively coupled to the power receiver application; a receiver RF antenna array arranged to receive and use RF power from the pockets of energy created by the wireless power transmitter at least partially responsive to the power receiver application.
 2. The system of claim 1, wherein the communication protocol used by the wireless communication hardware is one of Bluetooth Low Energy (BTLE) and WiFi.
 3. The system of claim 1, wherein the power transmitter manager application stores information obtained from the at least one wireless power receiver to facilitate communications between the wireless power transmitter and each respective wireless power receiver.
 4. The system of claim 3, wherein the information includes an identifier and location of the wireless power receiver.
 5. The system of claim 1, wherein the power transmitter manager application calls the transmitter API to perform a plurality of functions including: starting a connection; ending a connection; and sending data.
 6. The system of claim 1, wherein the transmitter API commands the transmitter wireless communication hardware according to the functions called by the power transmitter manager application.
 7. The system of claim 1, wherein the transmitter API calls the power transmitter manager application through a transmitter callback function.
 8. The system of claim 7, wherein the transmitter callback function sends a callback every time a communication connection begins, a communication connection ends, a communication connection is attempted, and a message is received.
 9. The system of claim 7, wherein a callback is sent ten times per second.
 10. The system of claim 1, wherein the wireless power receiver is at least one of an energy consuming electronic device and a cover of an energy consuming electronic device.
 11. The system of claim 1, wherein the power receiver application calls the receiver API to start a connection, end a connection, and send data.
 12. The system of claim 1, wherein the receiver API calls the power receiver application through a receiver callback function.
 13. The system of claim 12, wherein the receiver API sends a callback to the power receiver application when a connection begins, a connection ends, a connection is attempted, or a message is received.
 14. The system of claim 12, wherein the receiver API sends a callback to the power receiver application ten times per second.
 15. The system of claim 10 wherein the energy consuming device downloads a graphical user interface (GUI) from an application store to communicate with the power transmitter manager application.
 16. The system of claim 1, wherein the wireless power receiver sends to the wireless power transmitter information of the receiver including an identifier and location of the wireless power receiver.
 17. A wireless power transmitter comprising: a microprocessor running a power transmitter manager application; wireless communication hardware having an application programming interface (API) operatively coupled with the power transmitter manager application; and a transmitter radio frequency (RF) antenna array controlled by transmitter antenna manager software running on the transmitter microprocessor, arranged to form controlled RF waves that converge to create pockets of energy in the area proximate the wireless power transmitter responsive to the power transmitter application, which is responsive to the API.
 18. A wireless power receiver comprising: a microprocessor running a power receiver application; wireless communication hardware having a receiver API operatively coupled to the power receiver application; a receiver RF antenna array arranged to receive and use RF power from the pockets of energy created by the wireless power transmitter responsive to the power receiver application, which is responsive to the API.
 19. A method of wirelessly transmitting power comprising: broadcasting ads by a power receiver, wherein the ads include an identifier of the power receiver; receiving, by a power transmitter, at least one of the power receiver ads; initiating, by the power transmitter, a communication connection with the power receiver; sending information of the power receiver, by the power receiver, to the power transmitter; determining whether the power receiver is to be charged; in the case the power receiver is to be charged, tracking a position of the power receiver by the power transmitter; sending, by the power transmitter, a plurality of radio frequency waves that interfere constructively at the location of the power receiver to form a pocket of energy at the power receiver's position; and receiving the pocket of energy by the power receiver.
 20. The method of claim 19, further comprising: maintaining, by the power transmitter, information of a plurality of power receivers being tracked and which of the tracked power receivers are to be charged; and sending power pockets by the power transmitter to the receivers to be charged. 